domainCHPROV Request
Function
The CHPROV request is used to transfer a domain to one's own RegAcc for administration.
Requirements
- You can request a CHPROV only for domains which are administered by another RegAcc or the domains has been deletedand has the the „redemptionPeriod“ status. In this case, the domain is restored through a CHPROV with AuthInfo2 for the RegAcc that has submitted the request.
- Note that you can use only Contact handles of the requesting RegAcc in CHPROV requests. The handles must exist and fulfil the applicable conditions.
- The AuthInfo transferred with the CHPROV request must be identical with an AuthInfo1 or AuthInfo2 stored in DENIC's database.
Request Parameters
A CHPROV request is composed of the "Chprov" data object fields and of some other parameters, which are described below:
K/V Keyword | XML Namespace and Element | Occurrence min - max | Type / Length | Value Range | Description |
---|---|---|---|---|---|
Action | domain:chprov | 1 | enumeration | chprov-erule | This is the request type. |
Version | - | 1 | enumeration | version-erule | This is the version. The keyword is only relevant for requests in the key/value format. |
CtId | ctid | 0 - 1 |
token 3 - 64 |
Any visible Unicode character (according to Unicode version 3.1) | This is the unique transaction ID which is issued by the client. |
Common Mistakes
- The AuthInfo stated in the request does not match the AuthInfo(s) stored with DENIC.
- The domain is already under its own administration.
- The provider change shall be combined with a holder change, but the domain is bearing a DISPUTE entry.
Features
- A CHPROV may be combined with a holder change.
- If a CHPROV is executed by using an AuthInfo1, the existing AuthInfo1 will be deleted upon execution of the request; a possibly existing AuthInfo2 will be maintained if the Domainholder remains unchanged.
- If a CHPROV is executed by using an AuthInfo2, the Authinfo2 as well as any possibly existing AuthInfo1 will be deleted.
- If a DISPUTE has been placed on the domain concerned, a CHPROV request cannot be combined with a holder change.
- Domains can be restored from the Redemption Grace Period by means of a CHPROV with AuthInfo2.
Examples
- xml
- k/v
format: xml
request: domainCHPROV
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<registry-request xmlns="http://registry.denic.de/global/5.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:domain="http://registry.denic.de/domain/5.0" xmlns:dnsentry="http://registry.denic.de/dnsentry/5.0">
<domain:chprov>
<domain:handle>de-example.de</domain:handle>
<domain:contact role="holder">DENIC-1000002-MAX</domain:contact>
<domain:contact role="abusecontact">DENIC-1000002-ABUSE</domain:contact>
<domain:contact role="generalrequest">DENIC-1000002-GENERAL</domain:contact>
<dnsentry:dnsentry xsi:type="dnsentry:NS">
<dnsentry:owner>de-example.de</dnsentry:owner>
<dnsentry:rdata>
<dnsentry:nameserver>ns1.provider.de</dnsentry:nameserver>
</dnsentry:rdata>
</dnsentry:dnsentry>
<dnsentry:dnsentry xsi:type="dnsentry:NS">
<dnsentry:owner>de-example.de</dnsentry:owner>
<dnsentry:rdata>
<dnsentry:nameserver>ns2.provider.de</dnsentry:nameserver>
</dnsentry:rdata>
</dnsentry:dnsentry>
<domain:authInfo>secret</domain:authInfo>
<dnsentry:dnsentry xsi:type="dnsentry:DNSKEY">
<dnsentry:owner>de-example.de.</dnsentry:owner>
<dnsentry:rdata>
<dnsentry:flags>257</dnsentry:flags>
<dnsentry:protocol>3</dnsentry:protocol>
<dnsentry:algorithm>8</dnsentry:algorithm>
<dnsentry:publicKey>AwEAAajpN1rjU365IDVSd+duoMg4UF4S8zBSpJ4D/p2VSOKYVN7/0CkAV6pOhmdcoUMETA2LDPBWjEh4rrGiBN9ReRw/4udMgiEf3YyvsJEDpF6vtrWzqe+Cu9iu8QV//8ESlQgqK8TqVcR7e/FPd89R44S68GhZRFGw7h7sDrRnGIZf</dnsentry:publicKey>
</dnsentry:rdata>
</dnsentry:dnsentry>
</domain:chprov>
<ctid>cba-987654321</ctid>
</registry-request>
format: xml
response: domainCHPROV
status: connect
<?xml version="1.0" encoding="UTF-8"?>
<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
<tr:transaction>
<tr:stid>538f1687-963a-11df-a9e2-9519b5688882</tr:stid>
<tr:ctid>cba-987654321</tr:ctid>
<tr:result>success</tr:result>
<tr:message level="info" code="53000080013">
<tr:text>Domain "Status" is "connect"</tr:text>
</tr:message>
<tr:message level="info" code="16350000041">
<tr:text>Verification information must be provided for the holder(s) to avoid deletion by</tr:text>
<tr:argument>2024-12-16T15:45:01+01:00</tr:argument>
</tr:message>
<tr:message level="info" code="16350000040">
<tr:text>Verification information must be provided for the holder(s) to avoid dedelegation by</tr:text>
<tr:argument>2024-12-09T15:45:01+01:00</tr:argument>
</tr:message>
</tr:transaction>
</registry-response
format: xml
response: domainCHPROV
status: serverHold
<?xml version="1.0" encoding="UTF-8"?>
<registry-response xmlns="http://registry.denic.de/global/5.0" xmlns:tr="http://registry.denic.de/transaction/5.0">
<tr:transaction>
<tr:stid>538f1687-963a-11df-a9e2-9519b5688882</tr:stid>
<tr:ctid>cba-987654321</tr:ctid>
<tr:result>success</tr:result>
<tr:message level="info" code="53000080013">
<tr:text>Domain "Status" is "serverHold"</tr:text>
</tr:message>
<tr:message level="info" code="16350000041">
<tr:text>Verification information must be provided for the holder(s) to avoid deletion by</tr:text>
<tr:argument>2024-12-16T15:45:01+01:00</tr:argument>
</tr:message>
</tr:transaction>
</registry-response
format: k/v
request: domainCHPROV
Version: 5.0
Action: chprov
CTID: cba-987654321
Domain: de-example.de
Holder: DENIC-1000002-HOLDER
Generalrequest: DENIC-1000002-GENERAL
Abusecontact: DENIC-1000002-ABUSE
Nserver: ns1.beispiel-eins.de
Nserver: ns2.beispiel-eins.de
Dnskey: 257 3 8 AwEAAcoFUSyg1mkE5c33q8UbDiRZx5+/QtqFjVcyTEdv7YBYp9UnqrbXr7g4p8aDMI0ZuN4M8bxlPz+ItVfWO71rSkcxK1HwqmH4Pi1vSM3L6uYqZopEG9gJLqNpBBmzR29iSwR86TdnGUJ21Jfagc/+9xk3xmtdzNK3ROUcn/f8yiBN
Authinfo: secret
format: k/v
response: domainCHPROV
status: connect
Result: success
STID: 74ba5119-74d1-4ba6-935f-4feb07ddd14d
INFO: 53000080013 Domain "Status" is "connect"
INFO: 16350000040 Verification information must be provided for the holder(s) to avoid dedelegation by [2024-12-09T15:45:01+01:00]
INFO: 16350000041 Verification information must be provided for the holder(s) to avoid deletion by [2024-12-16T15:45:01+01:00]
Stid: 57ebbb10-9590-11df-a9e2-9519b5688882
Ctid: cba-9345345321
format: k/v
response: domainCHPROV
status: serverHold
Result: success
STID: 74ba5119-74d1-4ba6-935f-4feb07ddd14d
INFO: 53000080015 Domain "Status" is "serverHold"
INFO: 16350000041 Verification information must be provided for the holder(s) to avoid deletion by [2024-12-16T15:45:01+01:00]
Stid: 57ebbb10-9590-11df-a9e2-9519b5688882
Ctid: cba-9345345321